✅ Deploy Preview for devspace-docs ready!

Name	Link
🔨 Latest commit	3d1c959
🔍 Latest deploy log	https://app.netlify.com/projects/devspace-docs/deploys/69eafe1102ee4e0008673ee2
😎 Deploy Preview	https://deploy-preview-3232--devspace-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

From claude:

Adversarial Review — fix-docs branch

FAIL — Stale yarn.lock (medium)

mdx-mermaid@^v1.3.0 and mermaid@^11.12.3 are still present as orphaned top-level entries in docs/yarn.lock
(lines 8035 and 8085), even though both were removed from package.json. The lockfile was modified during
this PR (mermaid was bumped from 10.9.3 → 11.12.3 in an earlier step), but the final removal from
package.json wasn't followed by a yarn install to clean up. Running cd docs && yarn install will drop
those entries.

PASS — headingPrefix refactor

Logic is correct: depth + 1 preserves prior behavior, cap at 6 is the stated fix. All three boundary cases
in the test are correct (depth=1 → ## , depth=5 → ######, depth=8 → ######). GenerateReference starts at
depth=1 so depth=0 is unreachable in production — the test coverage is adequate.

PASS — Versioned sidebar ID stripping
Adversarial Review — fix-docs branch

FAIL — Stale yarn.lock (medium)

mdx-mermaid@^v1.3.0 and mermaid@^11.12.3 are still present as orphaned top-level entries in
docs/yarn.lock (lines 8035 and 8085), even though both were removed from package.json. The lockfile was
modified during this PR (mermaid was bumped from 10.9.3 → 11.12.3 in an earlier step), but the final
removal from package.json wasn't followed by a yarn install to clean up. Running cd docs && yarn install
will drop those entries.

PASS — headingPrefix refactor

Logic is correct: depth + 1 preserves prior behavior, cap at 6 is the stated fix. All three boundary
cases in the test are correct (depth=1 → ## , depth=5 → ######, depth=8 → ######). GenerateReference
starts at depth=1 so depth=0 is unreachable in production — the test coverage is adequate.

PASS — Versioned sidebar ID stripping

Removing version-4.x/ and version-5.x/ prefixes from doc IDs, and renaming "version-4.x/adminSidebar" →
"adminSidebar", is the correct Docusaurus 3 migration. Both files sharing the key "adminSidebar" is fine
— they're namespaced per-version internally.

PASS — Mermaid removal

No MDX file under docs/pages/ or docs/versioned_docs/ uses a component or mermaid fenced
block. The removal is clean. (The lockfile staleness above is the only artifact.)

PASS — Schema description fixes

The ${runtime.image.my-image.tag} → ${runtime.images.my-image.tag} typo (missing s) is consistently
fixed across all three files that mirror it: pkg/devspace/config/versions/latest/schema.go,
devspace-schema.json, and docs/schemas/config-openapi.json. ✓

PASS — patches.mdx import

FragmentInfoPrintConfig is imported and used at line 219. The partial (_partials/tip-print-config.mdx)
exists. ✓

One nitpick — test case name

The test case "top level" at depth=1 actually produces ## (h2), not h1. This is technically correct
since GenerateReference calls createSections with depth=1, but the name is slightly misleading. Not a
bug, but a reader could be confused.

Summary: One real fix needed — run cd docs && yarn install to remove the stale mermaid lockfile entries
before merging.